Clarify /start skill gate messages with intent classification#98
Merged
Conversation
Member
Author
Review SummaryVerdict: APPROVE Findings
No other issues found. The intent classification rules are consistent across all adapter files, the changes match the PR description, and the sync hashes are updated. No secrets, no security concerns. |
Member
Author
Review SummaryVerdict: APPROVE FindingsNo issues found. The previous WARNING about nested double quotes has been resolved — |
This was referenced Apr 11, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both human gate messages in the /start skill now suggest "go" as a fast-path shorthand and include agent-side intent classification rules — affirmative (proceed), affirmative with conditions (discuss first), questions (discuss), and abandonment (stop). This replaces the previous yes/no framing with clearer next-step options for Case A (approach confirmation) and Case B (resume confirmation).
Issue #96